home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.misc
- Path: news.sprintlink.net!eskimo!drizzit
- From: drizzit@eskimo.com (G. Baldwin)
- Subject: Re: OS features
- X-Nntp-Posting-Host: eskimo.com
- Message-ID: <DL5A59.16u@eskimo.com>
- Sender: news@eskimo.com (News User Id)
- Organization: Eskimo North (206) For-Ever
- X-Newsreader: TIN [version 1.2 PL2]
- References: <49tus6$os0@news.missouri.edu> <oj6n37uix5y.fsf@hpsrk.fc.hp.com>
- Date: Sun, 14 Jan 1996 00:17:33 GMT
-
- Steve Koren (koren@hpsrk.fc.hp.com) blessed us with these words of wisdom:
-
- : Anyway, I feel the Amiga could make a big step in the right direction by
- : starting out with just partial protection and phasing it in gradually.
- : For example, and a MEMF_PROTECTED tag to the types currently understood
- : by AllocVec/etc. This would allocate memory that couldn't be stomped by
- : another task. Programmers would have to use this explicitly, in order
- : to retain backwards source compatibility, but its better than nothing.
- : That, and you could protect code segments since they shouldn't be
- : written to. It wouldn't protect everything, but a few simple things
- : like that could go a *long* way towards increasing stability.
-
- Check out a program in the Aminet in the dev/misc/ directory called
- HackoRAM. From what I have read of the docs, it seems to use the
- 68040's MMU and Enforcer to handle "Cooperative Memory Protection".
- You have to recompile your software to take advantage of it, and it
- seems to still be in a BETA state, but what the hey...
-
- If you count PD Virtual Programs as "Amiga VMM routines", then you
- could also say that the Amiga has "Memory Protection routines" as well.
-
- : - steve
-
- -- Greg
-